Not really, the default order is last_run_start_date. Which I think is expected because you want to see dags that recently run first.

Why do you think dag_id makes more sense by default ?

I don't have a strong opinion, but using last_run_start_date as the default order keeps reordering the dags and makes it a little hard for me to find the dag I want to find. But I guess I just accept it at some point

We can go for dag_display_name by default if this is preferable. But that's not where this is done in the code.

  const orderBy = sort ? `${sort.desc ? "-" : ""}${sort.id}` : "-last_run_start_date";

We can go for dag_display_name by default if this is preferable. But that's not where this is done in the code.

  const orderBy = sort ? `${sort.desc ? "-" : ""}${sort.id}` : "-last_run_start_date";

Yep, dag_display_name is definitely way better than dag_id.

Thanks for pointing out. I've updated to use dag_display_name to sort. Also fix the mistake in connection default sort.

Is it perhaps better to make it configurable somewhere what you want to sort by? Different people might have different preferences of what to sort by.

It should be topological, falling back to the order it is added to the dag.

There is an existing bug for this

Sorry, totally misread this and thought it was about tasks

Make sense to make a config. I would try to implement it. Thanks!

Different people may want different sort order in the same instance too though. Maybe the sort choice should be sticky when you navigate away and back, instead of a global config.

Yeah, that makes sense. We do that for a bunch of stuff already with graph view, etc. We can do the same thing here as well.

Sure, I would open following PR for that. Thanks.

Backport successfully created: v3-0-test

Status	Branch	Result
✅	v3-0-test